Curse

Blackstream · Dec 18, 2006, 09:20 AM // 09:20

Is there any possibility to add into the code some "awaiting time" for the player connection?

This situation really hapens and is not seldom. You make Your way to a new city for example. All the way it is quite ok (despite of the lags, when the characters stop and after 3 seconds, You lie dead). But just before entering another location (or city), it disconnects with an error message. But after entering password again, You connect in seconds. So we're talking about possibile "lack of route" for 2 seconds? Let the servers wait for the player! For, let's assume, 10 seconds.

Otherwise, I turn to be afraid even to watch the cutscenes. Not to be disconnected after the whole (completed mission mainly).

Stupid Shizno · Dec 18, 2006, 10:07 AM // 10:07

If you get the end mission cutscene, or the symbol that shows your reward of the mission, even if you lag out you still get the next town/mission on your map...but will be relogged into the orginal mission town.

Blackstream · Dec 18, 2006, 11:28 AM // 11:28

Quote:

Originally Posted by Death3D

If you get the end mission cutscene, or the symbol that shows your reward of the mission, even if you lag out you still get the next town/mission on your map...but will be relogged into the orginal mission town.

That is absolutely true.
But it was maintained not long ago, because few month in the past - it didn't get You to the location (with quests at least).

But still - it would be nice if the server would wait for the player.
If there are more REAL players in the team, they might have a communicate in the town (waiting for the players to connect) or similar. Or even - the player would be incactive (just alike in the missions with "Slow loaders").